Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference: 474-tree-1
name: 1662
tree-preservation-order: undefined
474-tpo-1
uprn
address-text
point: POINT (-1.023805 50.882514)
geometry: MULTIPOLYGON (((-1.023719 50.882505,-1.023723 50.882522,-1.023735 50.882537,-1.023754 50.882549,-1.023777 50.882557,-1.023804 50.882560,-1.023830 50.882557,-1.023854 50.882550,-1.023873 50.882538,-1.023885 50.882523,-1.023890 50.882507,-1.023886 50.882490,-1.023874 50.882475,-1.023856 50.882463,-1.023832 50.882455,-1.023806 50.882452,-1.023779 50.882454,-1.023756 50.882462,-1.023736 50.882474,-1.023724 50.882488,-1.023719 50.882505)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL